-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix: API response for activating users returns 403 Forbidden #108
Conversation
@codesankalp can you please review it |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
QA-Checks and tests are showing as queued. Please make the suggested changes and let's see if the workflow runs again or not. @Amulya-coder
@codesankalp it's still failing! |
In my terminal, it's showing some errors like |
@Amulya-coder Follow the guidelines mentioned in README for QA-Checks and Testing. |
@codesankalp I have run black-checks and flake-checks everything looks fine. I think failing test isn't a major problem for this issue we can ignore this. |
@Amulya-coder This PR can't be merged if tests (QA-checks) do not pass. |
You can use the suggestions as mentioned in the actions. |
Ok @codesankalp I will try once again. |
@codesankalp QA checks are passed 👍 |
@codesankalp now can you please approve this. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@isabelcosta Needs your review in this PR. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍
I have tested it and it is working fine @devkapilbansal. |
Adding |
Thanks, @Amulya-coder for your contribution. 🚀 |
@Amulya-coder @codesankalp @devkapilbansal this is failing the tests, why is that 🤔 |
@isabelcosta You can trigger the workflow again but the workflow will fail due to a secret-key error. |
After merging of this #109 |
@isabelcosta locally it will pass all the build tests I have checked, here it shows due to the secret key as github requires the API key to trigger the workflow which is resolved by the codesankalp in #109 |
@Amulya-coder can you please update the branch? So the tests will pass? |
ok @isabelcosta I will update it by tomorrow. |
dd04649
@isabelcosta I have updated the branch, can you please review it, sorry for the delay. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cool! Thank you for your contribution @Amulya-coder 🎉
I will merge because latest changes were only to style with black formatting, and this was tested already by @codesankalp 🚀 |
Description
Adding the decorators separately to make the activation method available without any auth credentials.
Fixes #81
Type of Change:
Code/Quality Assurance Only
Checklist:
Code/Quality Assurance Only